-
Notifications
You must be signed in to change notification settings - Fork 41
Conversation
No need for the warning, funcion is no longer empty
TBTCSystem and DepositLog hold an independent copy of TBTCDepositToken TbtcSystem extedns DepositLog and theref ore the variable is shodowed. Instead of renaming and keeping both, using only the one from DepositLog is preferable
The return values are not used. On approvedToLog error revert isntead of returning false. Returning false offers the abhlity to not halt the deposit if approvedToLog returns false. This does not fel like a real perk. if approvedToLog returns false the event loger is not the deposit contract, and should revert.
|
setTbtcDepositToken should only be called internally
…nto log-refactor
@tintinweb, Not sure I follow. |
@tintinweb I assume #467 (comment) is the specific bit you're referencing. I think we're not currently aiming for the bigger refactor and just looking to keep this internal---is that right @NicholasDotSol ? |
yeah, I don't see a reason for a larger refactor now. We successfully de-duplicate by using Open to discussion of course |
Sorry I missed that conversation! The only point I had here is that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good.
refs: #467
TBTCDepositToken
shadow by removingTBTCSystem
's copyTBTCSystem
uses the one inherited fromDepositLog
.approvedToLog
fails.Deposit
contract would continue to function. It seems that this is not a real benefit. IfapprovedToLog
fails, the logging function is not called by theDeposit
contract and it makes sense to revert.